Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Phase 1 and Phase 2 processing stages

Table 5–2 describes the deployment stages of the DCU process.

Table 5–2: DCU deployment stages

Phase	Stage Order	Stage Name	Description
Phase 1–Apply schema updates (DCU session)	1	PreDelta	Use this stage for processing that became necessary after the last schema update was applied and that needs to occur before the new schema update is loaded.
	2	Delta	Use this stage to specify the name of the delta file for upgrading the schema to the new version.
	3	PostDelta	Use this stage to specify any upgrade programs that must take place before data is loaded into the schema. This is where most schema conversion programs are inserted.
	4	PreDataLoad1	This stage is rarely used. Use it to perform any processing that might be needed before data is loaded.
	5	DataLoad1	Use this stage to specify the list of .d files to be loaded after a schema update has been completed. For new databases, loading all the data from .d files is recommended, rather than using the ADO load mechanism.
	6	PostDataLoad1	This stage is rarely used. Use it to perform any processing that should take place after data is loaded into the database.
Phase 2–Apply data updates (Full Progress Dynamics session)	7	PreADOLoad	Use this stage to modify data prior to the loading of ADO datasets. Note that these changes might be overwritten by the load of the ADOs. Occasionally, that might be what you want to happen, but always consider the possibility for data loss. Also, note that the manager caches have not been built at this stage.
	8	ADOLoad	Use this stage to specify the names of the ADO dataset files that must be loaded to upgrade the database. Note that it is possible to place upgrade programs between ADO loads so that upgrade programs can be run between the load of different ADOs.
	9	PostADOLoad	Use this stage to perform any updates that must take place after the ADO datasets are loaded.
The data referred to here is data from .d files, not ADOs. It is loaded through the 4GL IMPORT statement and generally relies on the Data Dictionary's load_df.p program for loading into the database tables.